約 6,173,908 件
https://w.atwiki.jp/boare/pages/229.html
Release Note Release Date 6 Mar., 2010 Notes Cadencii requires ".NET Framework Runtime(version 2.0 or later)". Installer of this rumtime is available from the link below. .NET Framework Runtime Download .NET Framework 3.5 SP1 Cadencii can be launched with the latest version of mono. This enable you to use Cadencii with many platforms supported by mono. (Note Several functions using VOCALOID2 VSTi are not available in this case.) Mono is available from the link mono download Download Cadencii version 3.0.15 (1.2MB) How to get source codes Source code is available on SourceForege.JP. Please follow the instruction below for checking out the SourceForge.JP s SVN repository. svn checkout -r 894 http //svn.sourceforge.jp/svnroot/cadencii/branches/3.0 ./ These svn command is for checiking out "THIS" version of Cadencii. In order to get the latest source codes, please remove "-r" option.
https://w.atwiki.jp/boare/pages/149.html
Release Note Release Date 27 Sep., 2009 Notes Cadencii requires ".NET Framework Runtime(version 2.0 or later)". Installer of this rumtime is available from the link below. .NET Framework Runtime Download .NET Framework 3.5 SP1 Cadencii can be launched with the latest version of mono. This enable you to use Cadencii with many platforms supported by mono. (Note Several functions using VOCALOID2 VSTi are not available in this case.) Mono is available from the link mono download Download Cadencii version 2.3.5 (641KB) How to get source codes Source code is available on SourceForege.JP. Please follow the instruction below for checking out the SourceForge.JP s SVN repository. svn checkout -r 491 http //svn.sourceforge.jp/svnroot/cadencii/branches/2.3 ./ These svn command is for checiking out "THIS" version of Cadencii. In order to get the latest source codes, please remove "-r" option.
https://w.atwiki.jp/boare/pages/153.html
Release Note Release Date 27 Sep., 2009 Notes Cadencii requires ".NET Framework Runtime(version 2.0 or later)". Installer of this rumtime is available from the link below. .NET Framework Runtime Download .NET Framework 3.5 SP1 Cadencii can be launched with the latest version of mono. This enable you to use Cadencii with many platforms supported by mono. (Note Several functions using VOCALOID2 VSTi are not available in this case.) Mono is available from the link mono download Download Cadencii version 3.0.2 (1015KB) How to get source codes Source code is available on SourceForege.JP. Please follow the instruction below for checking out the SourceForge.JP s SVN repository. svn checkout -r 496 http //svn.sourceforge.jp/svnroot/cadencii/branches/3.0 ./ These svn command is for checiking out "THIS" version of Cadencii. In order to get the latest source codes, please remove "-r" option.
https://w.atwiki.jp/registry/pages/20.html
リンク RegSeekerの正しい？使い方 http //regseeker.nobody.jp/ TopTenREVIEWS http //toptenreviews.com/ WinXP消してもいいファイルまとめ http //deletable.fc2web.com/ 『このソフトを日本語化して欲しい！』スレッドまとめ http //www.wikihouse.com/windows/index.php?%C6%FC%CB%DC%B8%EC%B2%BD Download.com http //www.download.com/ FileForum http //fileforum.betanews.com/ Freeware Files.com http //www.freewarefiles.com/ MajorGeeks.com http //majorgeeks.com/ myfolder.net http //www.myfolder.net/ PCHome.de http //www.pchome.de/ PChome.net http //www.pchome.net/ SnapFiles http //www.snapfiles.com/ Softonic http //www.softonic.jp/ Softpedia http //www.softpedia.com/ softsea.net http //www.softsea.net/ The Portable Freeware Collection http //www.portablefreeware.com/ Tucows http //www.tucows.com/ Vector http //www.vector.co.jp/ ZDNet http //downloads.zdnet.com/ アルテック http //www.altech-ads.com/index.htm オールフリーソフト http //all-freesoft.net/ フリーソフト100 http //freesoft-100.com/
https://w.atwiki.jp/shoyofilms/pages/28.html
◆川柳 !DOCTYPE html html head meta http-equiv="X-UA-Compatible" content="IE=edge" meta charset="utf-8" title vue test /title meta name="viewport" content="width=device-width, initial-scale=1" style type="text/css" #result{ writing-mode vertical-rl; text-orientation upright; } /style /head body ?php echo "ok"; ? textarea id="source" onchange="rebuild2()" /textarea p id="result" aaa /p script const source = document.querySelector("#source"); const result = document.querySelector("#result"); function rebuild(){ const lines = source.value.split(/\n/); const lines2 = source.value.split(/\n/); const lines_size = lines.length; const r = " "; let char_count=0; let line_index=0; const longest = lines2.sort( function (a, b) { return b.length - a.length; } )[0]; const char_count_lim = longest.length; while(char_count char_count_lim){ if(lines[line_index][char_count]!=undefined){ r = r + " " + lines[line_index][char_count]; console.log(lines[line_index][char_count]); } line_index++; if(line_index =lines_size){ char_count++; line_index=0; } } result.innerHTML = r; } function rebuild2(){ result.innerHTML=source.value.replaceAll("\n"," br "); } /script /body /html ◆Download !DOCTYPE html html head meta http-equiv="X-UA-Compatible" content="IE=edge" meta charset="utf-8" title vue test /title meta name="viewport" content="width=device-width, initial-scale=1" style type="text/css" #canvas{ width 500px; height 500px; border 1px solid #000; } /style /head body canvas id="canvas" /canvas button id="download" download /button script document.getElementById("download").onclick = (event) = { let canvas = document.getElementById("canvas"); let link = document.createElement("a"); link.href = canvas.toDataURL("image/png"); link.download = "test.png"; link.click(); } /script /body /html ◆管理画面 html head meta charset="utf-8"/ style body{ margin 0; display flex; } aside{ width 200px; background #000; } /style /head body aside button onclick="load()" load csv /button /aside main input type="text" button onclick="save()" save /button /main script const input_txt = document.querySelector("input"); console.log(input_txt); function load(){ console.log("load"); fetch('test.txt') //.then(response = response.text()) .then(response = response.text()) .then(data = { console.log(data); input_txt.value=data; }); /* fetch('sample.csv') // (1) リクエスト送信 .then(response = response.text()) // (2) レスポンスデータを取得 .then(data = { // (3)レスポンスデータを処理 console.log(data); }); */ } function save(){ fetch('/admin/save.php?text=aaa') .then(response = { console.log(response); // (1) 通信が成功したか確認する if (!response.ok) { // (2) 通信に失敗したときはエラーを発生させる throw new Error('Not ok'); }else{ console.log("res ok"); } }); } /script /body /html ◆ファイル入出力 ?php // ファイルのパスを変数に格納 $filename = 'test.txt'; // fopenでファイルを開く（'w'は上書きモードで開く） $fp = fopen($filename, 'w'); // fwriteで文字列を書き込む fwrite($fp, "test aaa"); //$_REQUEST["text"] // ファイルを閉じる fclose($fp); // ファイルを出力する readfile($filename); ? ◆mermaid !DOCTYPE html html head meta http-equiv="X-UA-Compatible" content="IE=edge" meta charset="utf-8" title comment specifi /title meta name="viewport" content="width=device-width, initial-scale=1" style type="text/css" #code_view, #specifi{ display inline-block; border 1px solid #000; width 45%; min-width 200px; height 100vh; vertical-align top; padding 5px; } #code_view{ white-space pre; } /style /head body div id="code_view" /div div id="specifi" class="mermaid" #コメント @mermaid記法 graph TD; A-- B; /div script type="module" import mermaid from 'https //cdn.jsdelivr.net/npm/mermaid@10/dist/mermaid.esm.min.mjs'; /script script const code_view = document.querySelector("#code_view"); const code = '//初期化\n$a =3;\n$b =5;\n\n//合計\n$c = $a+$b;\n\necho $c;'; const code_rows = code.split(/\n/); code_rows.forEach(dog = { console.log(dog.name); }); const spec = code_rows.filter(c = { return c.indexOf('//') === 0; }); console.log(spec); /script /body /html ◆CSVEDITOR html head style body{ display flex; margin 0; } nav.csv_list{ min-width 170px; padding 10px; overflow auto; border-right 1px solid #000; } nav.csv_list ul{ list-style none; padding 0; } section.data{ overflow auto; padding 0 5px; } table { border 1px solid #000; } th, td{ border 1px solid #000; padding 0; } th input{ font-weight bold; } td input{ display inline; } nav.control{ margin-bottom 20px; /*display block;*/ } /style /head body nav class="csv_list" h2 CSV一覧 /h2 ul ?php $files = glob('*.csv'); foreach ($files as $key = $value) { echo " li a href='?open=".$value."' ".$value . ' /a /li '; } ? /nav section class="data" ?php if(isset($_REQUEST["open"]) file_get_contents($_REQUEST["open"])){ $file_name = $_REQUEST["open"]; $file = null; #データべースのファイルポインタ $is_indexed=false; $row; $column_name = []; $column_id=0; $row_num=0; echo " h2 {$file_name} /h2 nav class='control' button id='apply' 反映 /button button id='addleft' disabled 左に追加 /button button id='addright' disabled 右に追加 /button button id='addup' disabled 上に行追加 /button button id='deleterow' disabled 行削除 /button button id='adddown' disabled 下に行追加 /button /nav table id='data_table' "; if(file_exists($file_name)){ $file=fopen($file_name,"r"); while($row = fgetcsv($file)){ #データベースの列名変数を設定 if($is_indexed===false){ echo " tr td /td "; foreach($row as $r= $i){ ${"r_".$i} = $r; array_push($column_name,$i); echo " th input type='text' value='".$i."' id='h".$r."' class='select_column' /th "; } echo " /tr "; $column_num = $r+1; $is_indexed=true; }else{ echo " tr td class='select_row' id='r".$row_num."' 選 /td "; foreach($column_name as $c= $i){ $column_id = ${"r_".$i}; echo " td input type='text' value='".$row[$column_id]."' id='c".$row_num." ".($c+1)."' /td "; } echo " /tr "; } $row_num++; } echo " /table "; } } ? /section script const row_num= ?php echo $row_num; ? ; const column_num= ?php echo $column_num; ? ; let selected_row=""; let selected_column=""; button_addleft = document.getElementById("addleft"); button_addright = document.getElementById("addright"); button_addup = document.getElementById("addup"); button_deleterow = document.getElementById("deleterow"); button_adddown = document.getElementById("adddown"); data_table = document.getElementById("data_table"); button_addup.addEventListener("click", function() { const add_pos = parseInt(selected_row.substr(1)); var p = data_table.children[0].children; var q = data_table.children[0].children[1].cloneNode(true); console.log(q); data_table.children[0].children[add_pos].before(q); }); button_deleterow.addEventListener("click", function() { const del_pos = parseInt(selected_row.substr(1)); var aa = data_table.deleteRow(del_pos); console.log(del_pos, aa); }); button_adddown.addEventListener("click", function() { const add_pos = parseInt(selected_row.substr(1)); var p = data_table.children[0].children; var q = data_table.children[0].children[1].cloneNode(true); data_table.children[0].children[add_pos].after(q); }); button_addleft.addEventListener("click", function() { const add_pos = parseInt(selected_column.substr(1)); var aa = data_table.deleteRow( 1 ); console.log(add_pos, aa); }); function select_reset(){ var p = data_table.children[0].children; for(i=0; i p.length; i++){ p[i].children[0].style.backgroundColor = "#fff"; } for(i=0; i columns.length; i++){ columns[i].style.backgroundColor = "#fff"; } button_addleft.setAttribute("disabled",""); button_addright.setAttribute("disabled",""); button_addup.setAttribute("disabled",""); button_deleterow.setAttribute("disabled",""); button_adddown.setAttribute("disabled",""); } const rows = document.getElementsByClassName("select_row"); const trs = document.getElementsByTagName("tr"); for(i=0; i rows.length; i++){ rows[i].addEventListener("click", function() { select_reset(); this.style.backgroundColor = "#ff0"; tr_list = [].slice.call(trs); selected_row=tr_list.indexOf(this.parentNode); button_addup.removeAttribute("disabled"); button_deleterow.removeAttribute("disabled"); button_adddown.removeAttribute("disabled"); }); } const columns = document.getElementsByClassName("select_column"); const ths = document.getElementsByTagName("th"); for(i=0; i columns.length; i++){ columns[i].addEventListener("click", function() { select_reset(); this.style.backgroundColor = "#ff0"; th_list = [].slice.call(ths); selected_row=th_list.indexOf(this.parentNode); selected_column=this.id; button_addleft.removeAttribute("disabled"); button_addright.removeAttribute("disabled"); }); } document.getElementById("apply").addEventListener("click", function() { let csvtext = ""; for(c=0; c column_num; c++){ csvtext += document.getElementById("h"+c).value+","; } csvtext+="\r\n"; var p = data_table.children[0].children; for(i=1; i p.length; i++){ for(j=1; j p[i].children.length; j++){ csvtext += p[i].children[j].children[0].value +","; } csvtext+="\r\n"; } ////////////////////CSV形式へ変換//////////////////// // BOMを付与（Excelで開いた際のの文字化け対策） const bom = new Uint8Array([0xef, 0xbb, 0xbf]); // CSV用バイナリデータを作成 const blob = new Blob([bom, csvtext], { type "text/csv" }); // blobからオブジェクトURLを作成 const objectUrl = URL.createObjectURL(blob); ////////////////////ダウンロードリンクの作成とクリック//////////////////// // ダウンロードリンクを作成 ※HTMLのaタグを作成 const downloadLink = document.createElement("a"); // ファイル名の設定 const fileName = "sample.csv"; downloadLink.download = fileName; // ダウンロードファイルを設定 ※aタグのhref属性 downloadLink.href = objectUrl; // ダウンロードリンクを擬似的にクリック downloadLink.click(); // ダウンロードリンクを削除 downloadLink.remove(); }); /script /body /html ◆モーダル !DOCTYPE html html head meta http-equiv="X-UA-Compatible" content="IE=edge" meta charset="utf-8" title vue test /title meta name="viewport" content="width=device-width, initial-scale=1" style type="text/css" /style /head body dialog !-- モーダルウィンドウ内のテキストの指定 -- p これはモーダルダイアログのウィンドウ画面です /p !-- モーダルウィンドウ内を閉じるボタンの指定 -- button id="close" モーダルウィンドウを閉じる /button /dialog !-- モーダルウィンドウ内を開くボタンの指定 -- button id="open" モーダルウィンドウを開く /button aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br aaa br script let dialog = document.querySelector('dialog'); // dialog（モーダルダイアログ）の宣言 let btn_open = document.getElementById('open'); // open（開く）ボタンの宣言 let btn_close = document.getElementById('close'); // close（閉じる）ボタンの宣言 btn_open.addEventListener('click', function() { // 開くボタンをクリックした場合の処理 dialog.showModal(); }, false); btn_close.addEventListener('click', function() { // 閉じるボタンをクリックした場合の処理 dialog.close(); }, false); /script /body /html ◆HTML生成 !DOCTYPE html html head meta http-equiv="X-UA-Compatible" content="IE=edge" meta charset="utf-8" title vue test /title meta name="viewport" content="width=device-width, initial-scale=1" style type="text/css" /style /head body form action="gen.php" method="post" input type="submit" value="gen" /input /form /body /html gen.php ?php exec("php e.php t2.html"); header("Location /static/"); ? e.php ?php $test = "aaa"; $model=" !DOCTYPE html html head meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\" meta charset=\"utf-8\" title vue test /title meta name=\"viewport\" content=\"width=device-width, initial-scale=1\" style type=\"text/css\" /style /head body ".$test." /body /html "; echo $model; ◆スキル !DOCTYPE html html head meta http-equiv="X-UA-Compatible" content="IE=edge" meta charset="utf-8" title test /title meta name="viewport" content="width=device-width, initial-scale=1" style type="text/css" details{ margin 0 0 -10px; padding 0; } summary{ font-family Impact; font-style italic; list-style none; font-size 50px; height 50px; border-bottom 1px solid #000; margin 0; padding 0; transition 1s; } summary hover{ color #fa0; } /style /head body details summary HTML /summary dl dt 項目1 /dt dt 項目2 /dt dt 項目3 /dt /dl /details details summary HTML2 /summary dl dt 項目1 /dt dt 項目2 /dt dt 項目3 /dt /dl /details /body /html
https://w.atwiki.jp/nihongodocuments/pages/14.html
Lerning Center The following groups of documents provide useful information for users and developers of xTuple ERP. xTuple ERPのユーザーと開発者に役立つ情報が書かれたドキュメントをグループに分類しています。 xTuple.org-Admin and Setup The Administration and Setup area contains essential information for setting up xTuple ERP, with an emphasis on installing the database and configuring Postgres for Linux, Mac, and Windows. This area also includes information about important Release Updates. 「管理と設定」では、Linux, Mac, Windows各マシンへの、データベースのインストール、Postgresの設定に要点を置き、xTuple ERPをセットアップする基本的な情報が書かれています。 xTuple.org-Demo Videos We offer an extensive list of free demo videos that provide training for xTuple ERP and demonstrations of the latest advanced features of the software. xTuple ERPのトレーニング、および最新の高度な機能をデモンストレーションする無料のデモビデオをご提供します。 xTuple.org-Topics The documents in this section are guides for understanding and using the xTuple ERP application. The contents are divided into sections based on the functional areas of the software, such as accounting, manufacturing and sales. There are also miscellaneous topics, including how to import data from QuickBooks, ad hoc reporting, and more. Read more » この章ではxTuple ERPアプリケーションを理解し、利用するガイドとなるドキュメントを提供します。会計、生産、販売といったソフトウェアの機能ごとに、本章のドキュメントは分割されています。更に、QuickBooksからのデータ移行方法、レポート、その他のトピックスも含まれています。 xTuple.org-Developer Zone Welcome! The Developer Zone is the place to learn about extending xTuple with scripted packages, modifying core source code, and interfacing with third party applications. Read more » Developper Zoneは、スクリプトパッケージによるxTupleの機能拡張、ソースコードの改変、サードパーティアプリケーションなどを学習する場所です。 xTuple.org-Demo Guide This Demo Guide is intended for users of the "Free Hosted Demo" of xTuple ERP Manufacturing Edition. Before you begin, you should apply for a free demo account and download the xTuple client software. Read more » 製造業向けxTuple ERPの"Free Hosted Demo"用デモガイドです。デモの開始前に、無料のデモアカウントの取得、xTupleクライアントをダウンロードする必要があります。 xTuple.org-Product Guides This section contains the official Reference Guide for each numbered release of xTuple ERP, as well as Product Guides for add-ons and xTensions. Read more » この章では、アドオンや拡張といったプロダクトガイドと同様に、xTuple ERPの公式リファレンスガイドを用意しています。 xTuple.org-OpenRPT The Product Guide guide and reference material for OpenRPT, the free report writer included with xTuple ERP and available for free download. Read more » xTuple ERPに含まれており、またフリーにダウンロードできる、レポート作成ソフト「OpenRPT」のユーザーガイドと、機能リファレンスです。 xTuple.org-Translation and Localization The worldwide xTuple community has been hard at work creating translations in more than twenty languages. These can be downloaded directly from our Translation Portal. You can also find instructions for installing and using language files, or join one of the translation teams to contribute to a translation. Read more » 世界的なxTupleコミュニティは、20カ国以上の翻訳機能を作製しました。これは翻訳ポータルからダウンロードできます。ランゲージファイルのインストール方法、使用方法が見つけられます。また、翻訳チームに加わり、貢献することもできます。 xTuple.org-Third-Party Solutions This section includes guides and instructions for using third-party extensions developed for xTuple ERP. The extensions themselves are available for download in the xChange. Read more » この章は、xTuple ERPのサードパーティ拡張機能の開発者向けガイドです。 xTuple.org-Web Integration This section contains documentation for various web-based interfaces for interacting with the xTuple ERP database. Our approach is to create web interfaces where it makes the most sense--we are not replacing the GUI client with a web-based interface, but rather to expose specific functionality to the web, where it would be useful to have additional inputs from customers, partners, etc. Read more » このセクションでは、xTuple ERPのデータベースと対話するための様々なウェブベースのインターフェイスに関するドキュメントが含まれています。我々のアプローチは、それが最も理にかなってどこのWebインターフェースを作成することです - 私たちはWebベースのインタフェースとGUIクライアントを交換されるのではなく、それは顧客からの追加入力を持つことが有用であろう場所、ウェブへの特定の機能を公開する、パートナー、等
https://w.atwiki.jp/stones/pages/205.html
■Definitely Vintage (Mickboy Remaster) (Tone Frayed Productions T F 001), Los Angeles show 1-18-73. (2CDR) ■This is the only Honolulu show on 1-21-73 recorded on tape. The tape was around before all of the above bootleg releases-- the sound is equal to, if not better than, all of them. (untitled 1CDR transferred from audio tape) ■Complete show from 1-22-73 Honolulu 2nd show in same low sound quality recorded on CDR from audio cassette tape (tracks set manually). (untitled 1CDR transferred from audio tape) ■2-11-73 Auckland show. (untitled 1CDR transferred from audio tape) ■2-14-73 Brisbane, This is the tape source for the above bootleg CD releases. Brown Sugar is missing the first two minutes. (untitled 1CDR transferred from audio tape) ■Complete show from 2-17-73 Melbourne 1st show recorded in average sound quality to CDR from audio cassette tape (tracks set manually). (untitled 1CDR transferred from audio tape) ■The Lost Melbourne 1973, Incomplete show, only 7 tracks. The long lost 2-17-73 Melbourne 2nd show recorded in poor quality. Absolutely one of the worst recordings I ve ever heard in my entire life. (1CDR) ■Complete show from 2-18-73 Melbourne recorded in average sound quality. Probably the tape source for the above bootleg CD releases which it procedes. Sound quality is about the same, but the tape runs about four minutes longer. (untitled 2CDR transferred from audio tape) ■2-18-73 Melbourne Show, Best Selection Source. (untitled 1CDR transferred from audio tape) ■Complete show from 2-20-73 Adelaide recorded in slightly below average sound quality. (untitled 1CDR transferred from audio tape) ■The Band s On Stage, Complete show from 2-20-73 Adelaide recorded in slightly below average sound quality. (2CDR) ■The Riot Show and More, Disc 1 2 are the complete 2-20-73 Adelaide show and the 2-16-73 Melbourne Press Conference. (3CDR-disc 1 2) ■2-21-73 Adelaide show. (untitled 1CDR transferred from audio tape) ■I Think It s Gonna Rain Again Tonight, 2-21-73 Adelaide show. (1CDR) ■The Riot Show and More, Disc 3 is the complete 2-21-73 Adelaide show. (3CDR-disc 3) ■Ten tracks from 2-24-73 Perth in excellent soundboard quality transferred to CDR from audio tape (tracks set manually). Wrong track succession. (untitled 1CDR transferred from audio tape) ■Complete 2-26-73 Sydney show soundboard (last 2 songs audience) + 3 extra 1973 soundboards All Down the Line (7-22-72) Midnight Rambler (2-27-73) Street Fighting Man (2-27-73). (untitled 2CDR transferred from audio tape) ■Stones on the Barbie, The complete 2-27-73 Sydney show in excellent stereo soundboard quality. (1CDR) ■This audio tape version of the 9-1-73 Vienna show was for many years superior to the LP and CD releases (until the mostrecent VGP bootleg CD listed above. (untitled 2CDR transferred from audio tape) ■Complete show from 9-3-73 Mannheim recorded in slightly below average quality. Includes rare 1973 European Toursongs Bitch 100 Years Ago Sweet Virginia (untitled 2CDR transferred from audio tape) ■Eau De Cologne 1973, Sixteen tracks from 9-4-73 Cologne 2nd show (eight from audience source, ten from soundboard source). A lot of cuts in soundboard tracks, but still this is a gem. (2CDR) ■Cologne 1973, Ten soundboard tracks from 9-4-73 Cologne 2nd show. A lot of cuts in soundboard tracks, but still this is a gem. (2CDR) ■Eau De Cologne 1973, Cologne 2nd show. (1CDR) ■The complete 9-4-73 Cologne 2nd show recorded in absolutely terrible audience quality. One of the worst recordings I ve ever heard in my entire life. (untitled 2CDR transferred from audio tape) ■9-7-73 London show recorded in not very good sound quality. (untitled 1CDR transferred from audio tape) ■9-7-73 London show recorded in not very good sound quality. (untitled 1CDR transferred from audio tape) ■9-8-73 London 1st show recorded in not very good sound quality. (untitled 1CDR transferred from audio tape) ■9-8-73 London 1st show recorded in not very good sound quality. (untitled 1CDR transferred from audio tape) ■Thirteen tracks from 9-8-73 London 2nd show compiled from two sources; Live in London LP (FF RS-2001) Come Back London 73 CD (Alley Cat). (untitled 1CDR transferred from audio tape) ■Complete show 9-9-73 London recorded in not very good sound quality. This is an audience recording, not FM soundboard. The grand finale concert climax Street Fighting Man is the best ever. (untitled 1CDR transferred from audio tape) ■9-9-73 London show, Best selection source. (untitled 1CDR transferred from audio tape) ■The complete 9-16-73 Glasgow show recorded in even worse sound quality.. (untitled 1CDR transferred from audio tape) ■The complete 9-16-73 Glasgow show recorded in even worse sound quality.. (untitled 1CDR transferred from audio tape) ■Dancing with Mr. M, The complete 9-16-73 Glasgow show recorded in not very good sound quality. (1CDR) ■Live in Scotland, The complete 9-16-73 Glasgow show recorded in not very good sound quality. (1CDR) ■Birmingham Odeon 1973 Revisited! (9-19-73), Remaster of the Oh Boy CD Birmingham Odeon 1973 with not very significant improvement. (1CDR) ■The 9-25-73 Berne show recorded in worse audience quality. This was thought once to be 9-26-73 Berne 2nd show, but this is incorrect. This is the only show on 9-25-73. (untitled 1CDR transferred from audio tape) ■This is the 9-26-73 Berne 1st show from tape source. Much worse quality than the VGP CD Swiss Made (untitled 1CDR transferred from audio tape) ■The Lost Berne Show (SWP-533), 6 tracks supposedly from the lost 9-26-73 Berne 2nd show, but I have my doubts. The confusion over the 3 Berne shows is so bad that I doubt anyone really knows for sure. (1CDR) ■9-28-73 Munich 1st show recorded in terrible sound quality. (untitled 1CDR transferred from audio tape) ■An Afternoon in Munich, The 9-28-73 Munich 1st show recorded in terrible sound quality. (1CDR) ■An Evening in Munich, Complete show from 9-28-73 Munich 2nd show in about average sound quality. This recording runs longer, but the quality is not as good as that above. (2CDR) ■9-30-73 Frankfurt 1st show. (untitled 1CDR transferred from audio tape) ■9-30-73 Frankfurt 2nd show. (untitled 1CDR transferred from audio tape) ■Complete show from 10-2-73 Hamburg 1st show recorded in terrible sound quality. (untitled 1CDR transferred from audio tape) ■Give Me a Hamburger, Complete show from 10-2-73 Hamburg 1st show recorded in terrible sound quality. This bootleg CD contains both Hamburg 1973 shows. (2CDR-disc 1) ■Give Me a Hamburger, Complete show from 10-2-73 Hamburg 2nd show recorded in terrible sound quality. This bootleg CD contains both Hamburg 1973 shows. (2CDR-disc 2) ■Complete 1st show from 10-6-73 Gothenburg recorded in average sound quality. A nice show. (untitled 1CDR transferredfrom audiotape) ■Heartbreakers at the Scandinavium, 10-6-73 Gothenburg 1st show. (1CDR) ■10-7-73 Copenhagen 1st show. (untitled 1CDR transferred from audio tape) ■10-7-73 Copenhagen 2nd show. (untitled 1CDR transferred from audio tape) ■10-9-73 Essen show. (untitled 1CDR transferred from audio tape) ■Brown Sugar and White Snow Remastered, 10-9-73 Essen show. (1CDR) ■More Brown Sugar and White Snow, Fourteen tracks from 10-10-73 Essen in average quality. Excellent performance. (1CDR) ■The Stars in the Sky they Never Fall, 10-10-73 Essen show. (2CDR) ■The complete 10-13-73 Rotterdam show recorded in terrible sound quality on CDR. (untitled 1CDR transferred from audio tape) ■The First Night in Rotterdam, The complete 10-13-73 Rotterdam show recorded in terrible sound quality on CD title. (1CDR) ■The complete 10-14-73 Rotterdam 1st show recorded in not very good sound quality. (untitled 2CDR transferred from audio tape) ■Best Wishes and Love, The complete 10-14-73 Rotterdam 1st show recorded in not very good sound quality. (1CDR) ■10-14-73 Rotterdam 2nd show. (untitled 2CDR transferred from audio tape) ■Round and Round we go to Rotterdam, Extremely rare--this is the authentic 10-14-73 Rotterdam 2nd show recorded in the worst possible quality (missing only the first track). (1CDR) ■The complete 10-15-73 Antwerp 1st show recorded in terrible audience quality from an alternate source. Vocals are clear, but band is distorted and muddy. Midnight Rambler is complete here. (untitled 1CDR transferred from audio tape) ■Low GEN audience tape source for the complete 10-17-73 Brussels 1st show in much better quality than the VGP CD Nasty Muzik (VGP-252) audience tape source. Rare! (untitled 1CDR transferred from audio tape) ■Nasty Music, 10-17-73 Brussels 1st show. (1CDR) ■Once thought to be the 10-15-73 Antwerp 2nd show, this is actually five great soundboard tracks from the 10-17-73 Brussels 2nd show. A gem. (untitled NZ 1CDR) ■Bobby Keys missed this final show of 1973 European Tour due to a drug overdose. This NZ tape authenticating 10-19-73 Berlin show includes German radio commentary. (untitled 2CDR transferred from audio tape) ■10-19-73 Berlin show. (untitled 1CDR transferred from audio tape) ■Missing Links, 12 tracks mostly from KBFH FM broadcasts all from the 1973 European Tour and in very nice quality. (1CDR) BACK / NEXT
https://w.atwiki.jp/testlink/pages/41.html
!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd" !-- Japanese Translated by Testing Engineer s Forum (TEF) in Japan, Working Group of TestLink Japanese Translation Project -- html xmlns="http //www.w3.org/1999/xhtml" lang="jp" head meta http-equiv="Content-Type" content="text/html; charset=UTF-8" / meta http-equiv="Content-language" content="jp" / meta name="author" content="Martin Havlat" / meta name="copyright" content="GNU" / meta name="robots" content="NOFOLLOW" / title TestLink Help Glossary of Terms /title link rel="stylesheet" type="text/css" href="{$basehref}{$smarty.const.TL_THEME_CSS_DIR}tl_docs.css" / /head body h1 TestLinkで使用されている用語の注解 /h1 div id="menu" a href="javascript window.close();" class="tlButton" 閉じる /a a href="javascript history.back();" class="tlButton" 戻る /a a href="{$basehref}lib/general/show_help.php?help=content locale={$locale}" class="tlButton" ヘルプ 目次 /a /div h2 範囲 /h2 p この資料は設計概念を表示しています、 用語と定義はテストの専門用語を理解することに役立ちます。 イタリック体の説明はTestLinkの語法です。 /p h2 定義 /h2 ul li a name="actualoutcome" /a b 実際の結果 /b テストでコンポーネントやシステムが出力、表示した結果。 /li li a name="bug" /a b バグ /b (= a href="#fault" フォールト /a )要求された機能をコンポーネントまたはシステムに果たせなくする、コンポーネントまたはシステム中の不備。たとえば不正な命令、データ定義。実行中に欠陥に遭遇した場合、コンポーネントまたはシステムの故障を引き起こす。 /li li a name="coverageitem" /a b カバレッジ アイテム /b a href="#testing" テスト /a /li カバレッジの基礎となる実体や属性。たとえば同値分割やコード命令。 li a name="error" /a b エラー /b 間違った結果を生み出す人間の行為。 /li li a name="expectedresults" /a b 予想結果 /b (= 予測結果 または 予想結果)指定の条件下で a href="#testspec" 仕様 /a やほかの情報から予測できるコンポーネントやシステムの動作。 /li li a name="failure" /a b 故障 /b コンポーネントやシステムが期待した機能、サービス、結果を提供できないこと。 /li li a name="fault" /a b フォールト /b (= バグ)要求された機能をコンポーネントまたはシステムに果たせなくする、コンポーネントまたはシステム中の不備。たとえば不正な命令、データ定義。実行中に欠陥に遭遇した場合、コンポーネントまたはシステムの故障を引き起こす。 /li li a name="steps" /a b ステップ /b (= テストシナリオ, 入力)開始点から終了点に至る一連のテスト実行のアクション /li li a name="testproject" /a b テストプロジェクト /b span class="italic" テストプロジェクトはTestLinkデータの一番上位の構造です。 すべてのデータ(ユーザ情報を除いて)は活動しているテストプロジェクトに関連付けられます。 /span /li li a name="testcasesuite" /a b テストケーススイート /b 対象のコンポーネントまたはシステムのために a href="#testcase" テストケース /a をまとめたもの。ひとつのテストの事後条件は次のテストの前提条件として利用される。 span class="italic" TestLinkではテスト仕様またはテスト計画でテストケースをまとめるために使用される。 /span /li li a name="testcoverage" /a b テストカバレッジ /b 指定の網羅条件を a href="#testcasesuite" テストスイート /a が実行した度合。パーセンテージで表す。 /li li b a name="testexecution" /a テスト実行 /b テスト対象のコンポーネントやシステムでテストを実行し a href="#actualoutcome" 実際の結果 /a を出力するプロセス。 br/ span class="italic" テストケーススイートはテストケースから割り当てられたテスト仕様でテストケースを定義している。 /span /li li a name="testplan" /a b テスト計画 /b 計画されたテスト活動の狙い、アプローチ、リソーススケジュールを記述するドキュメント。テストアイテム、テストすべき特色となる機能、テスティングタスク、各タスクを行う人、テスト担当者の独立の度合い、テスト環境、使われるテスト設計技法と入口・出口基準、それらの選択の理論的根拠、それに代替計画を必要とするあらゆるリスクを特定する。これはテスト計画プロセスの記録である。 br/ span class="italic" TestLinkはテスト計画にてユーザの割り当て、ビルド、テストケーススイートを定義できる。 /span /li li a name="testspec" /a b テスト仕様 /b 各々の a href="#testcase" テストケース /a 、 a href="#coverageitem" カバレッジアイテム /a 、テストにおけるソフトウェアの初期状態、 a href="#steps" ステップ /a 、そして a href="#expectedresults" 予想結果 /a 。 /li li a name="testing" /a b テスト /b ひとつ以上のテストケースの組み合わせ /li li a name="testcase" /a b テストケース /b a href="#steps" ステップ /a 、実行前条件値、 a href="#expectedresults" 予想結果 /a そして実行事後条件の組み合わせで、特定のプログラムのシナリオを用いることや指定された要件の遵守を検証することのような特定の目的またはテスト条件のために開発されたもの。 /li /ul /body /html
https://w.atwiki.jp/matchmove/pages/74.html
Exporting to Your Animation Package Once you are happy with the object paths and tracker positions, use the Export menu items to save your scene. The following options are currently available (note that this list is constantly being expanded; check the web site) · 3ds max 4 or later (Maxscript). Should be usable for 3D Studio MAX 3 as well. Separate versions for 3dsmax 5 and earlier, and 3dsmax 6 and later. · After Effects (via a special maya file) · Bentley Microstation · Blender · Carrara · Cinema 4D (via Lightwave scene) · Combustion · ElectricImage (less integrated due to EI import limitations) · FLAIR motion control cameras (Mark Roberts Motion Control) · Flame (3-D) · Fusion 5 · Hash Animation Master. Hash 2001 or later. · Houdini · Inferno 3-D Scene. · Lightwave LWS. Use for Lightwave, Cinema 4D · Maya scene file · Mistika · Motion – 2-D · Nuke (D2 Software, subsidiary of Digital Domain) · Particle Illusion · Poser · Realsoft 3D · Shake (several 2-D/2.5-D plus Maya for 3-D scenes) · SoftImage XSI, via a dotXSI file · Toxik · trueSpace · Vue 5 and 6 Infinite · VIZ (via 3ds Max scene) SynthEyes offers a scripting language, SIZZLE™, that makes it easy to modify the exported files, or even add your own export type. See the separate SIZZLE User Manual for more information. New export types are being added all the time, check the export list in SynthEyes and the support site for the latest packages or beta versions of forthcoming exporters. General Procedures You should already have saved the scene as a SynthEyes file before exporting. Select the appropriate export from the list in the File/Exports area. SynthEyes keeps a list of the last 3 exporters used on the top level of the File menu as well. Hint SynthEyes has many exports. To simplify the list, clickScript/System Script Folder, create a new folder “Unused” in it, and move all the scripts for applications you do not use into that folder. You will have to repeat this process when you later install new builds, however. There is also an export-again option, which repeats the last export performed by this particular scene file, with the most-recently-used export options, without bring up the export-options dialog again to save time for repeated exports. When you export, SynthEyes uses the file name, with the appropriate file extension, as the initial file name. By default, the exported file will be placed in a default export folder (as set using the preferences dialog). In most cases, you can either open the exported file directly, or if it is a script, run the script from your animation package. For your convenience, SynthEyes puts the exported file name onto the clipboard, where you can paste it (via control-V or command-V) into the open-file dialog of your application, if you want. (You can disable this from the preferences panel if you want.) Note that the detailed capabilities of each exporter can vary somewhat. Some scripts offer popup export-control dialogs when they start, or small internal settings at the beginning of each Sizzle script. For example, 3ds max does not offer a way to set the units from a script before version 6 and the render settings are different, so there slightly different versions for 3dsmax 5 and 6+. Settings in the Maya script control the re-mapping of the file name to make it more suitable for Maya on Linux machines. If you edit the scripts, using a text editor such as Windows’ Notepad, you may want to write down any changes as they must be re-applied to subsequent upgraded versions. Be aware that not all packages support all frame rates. Sometimes a package may interpret a rate such as 23.98 as 24 fps, causing mismatches in timing later in the shot. Or one package may produce 29.96 vs 29.97 in another. Handle image sequences and use frame counts rather than AVIs, QTs, frame times, or drop-frame time codes wherever possible. TheCoordinate System control panel offers an Exportable checkbox that can be set for each tracker. By default, all trackers will be exported, but in some cases, especially for compositors, it may be more convenient to export only a few of the trackers. In this case, select the trackers you wish to export, hit control-I to invert the selection, then turn off the checkbox. Note that particular export scripts can choose to ignore this checkbox. Setting the Units of an Export SynthEyes uses generic units a value of 10 might mean 10 feet, 10 meters, 10 miles, 10 parsecs—whatever you want. It does not matter to SynthEyes. This works because match-moving never depends on the overall scale of the scene. SynthEyes generally tries to export the same way as well—sending its numbers directly as-is to the selected animation or compositing package. However, some software packages use an absolute measurement system where, for instance, Lightwave requires that coordinates in a scene file always be in meters. If you want something else inside Lightwave, it will automatically convert the values. For such software, SynthEyes needs to know what units you consider yourself to be using within SynthEyes. It doesn’t care, but it needs to tell the downstream package the right thing, or pre-scale the values to match your intention. To set the SynthEyes units selection, use the Units setting on the SynthEyes preferences panel. Changing this setting will not change any numbers within SynthEyes; it will only affect certain exports. The exports affected by the units setting are currently these · After Effects (3-D) · Hash Animation Master · Lightwave · 3ds max · Maya · Poser Before exporting to one of these packages, you should verify your units setting. Alternatively, if you observe that your imported scene has different values than in SynthEyes, you should check the units setting in SynthEyes. Hint if you will be exporting to acompositing package, they often measure everything, including 3-D coordinates, in terms of pixels, not inches, meters, etc. Be sure to pick sizes for the scene that will work well in pixels. While you might scale a scene for an actor 2m tall, if you export to a compositor and the actor is two pixels tall that will rarely make sense. Image Sequences Different software packages have different conventions and requirements regarding the numbering of image sequences whether they start at 0 or 1, whether there are leading zeroes in the image number, and whether they handle sequences that start at other numbers flexibly. For example, if you have a shot that originally had frames img1.tif-img456.tif, but you are using only images img100.tif-img150.tif of it, SynthEyes will normally consider it as a 51 frame shot, starting with frame 0 (img100.tif) or, withFirst frame is 1preference on, as frame 1 at img100.tif. Other software sometimes requires that their frame numbers match the file number, so img100.tif must always be frame 100, no matter what frame# they normally start at. SynthEyes gives you the option to pad the beginning of IFLs with extra copies of the first frame, so that the SynthEyes frame number matches the image frame number, by turning on the Match frame# s preference. While this sounds simple, it will cause trouble for many of the exports. It is especially a problem if you do not have the unused frames, as is often the case. By being aware of these differences, you will be able to recognize when your particular situation requires an adjustment to the settings—typically when there is a shift between the camera path animation and the imagery. Generic 2-D Tracker Exporters There are a number of similar exporters that all output 2-D tracker paths to various compositing packages. Why 2-D, you protest? For starters, SynthEyes tracking capabilities can be faster and more accurate. But even more interestingly, you can use the 2-D export scripts to achieve some effects you could not with the compositing package alone. For image stabilizing applications, the 2-D export scripts will average together all the selected trackers within SynthEyes, to produce a synthetic very stable tracker. For corner-pinning applications, you can have SynthEyes output not the 2-D tracker location, but the re-projected location of the solved 3-D point. This location can not only be smoother, but continues to be valideven if the tracker goes off-screen. So suppose you need to insert a painting into an ornate picture-frame using corner pinning, but one corner goes off-screen during part of the shot. By outputting the re-projected 3-D point (Use solved 3-D points checkbox), the corner pin can be applied over the entire shot without having to guess any of the path. Taking this idea one step further, you can create an “extra” point in 3-D in SynthEyes. Its re-projected 2-D position will be averaged with any selected trackers; if there are none, its position will be output directly. So you can do a four-corner pin even if one of the corners is completely blocked or off-screen. By repeating this process several times, you can create any number of synthetic trackers, doing a four-corner insert anywhere in the image, even where there are no trackable features. Of course, you could do this with using a 3-D compositing environment, but that might not be simplest. At present, there are compatible 2-D exporters for AfterEffects, Digital Fusion, Discreet (Combustion/Inferno/Flame), Particle Illusion, and Shake. Note that you will need to import the tracker data file (produced by the correct SynthEyes exporter) into a particular existing tracker in your compositing package. There is also a 2-D exporter that exports all tracker paths into a single file, with a variety of options to change frame numbers and u/v coordinates. A similar importer can read the same file format back in. Consequently, you can use the pair to achieve a variety of effects within SynthEyes, including transferring trackers from SynthEyes file to SynthEyes file, as described in the section onMerging Files and Tracks. This format can also be imported by Fusion. Generic 3-D Exporters There are several 3-D exports that produce plain text files. You can use them for any software SynthEyes don’t already support, for example, non-visual-effects software. You can also use them as a way to manipulate data with little shell, AWK, or Perl scripts, for example. Importantly, you can also use them as a way to transfer data between SynthEyes scene files, for example, to compute some tracker locations to be used by a number of shots. There are several ways to do this, see the section onMerging Files and Tracks. The generic exports are Camera/Object Path for a path, Plain Trackers for the 3-D coordinates of trackers and helper points, and corresponding importers. You can import 3-D locations to create either helper points, or trackers. This latter option is useful to bring in surveyed coordinates for tracking. After Effects 3-D Procedure 1. Export to After Effects in SynthEyes to produce a (special) .ma file. 2. In After Effects, do a File/Import File 3. Change Files of Type to All File Formats 4. Select the .ma file 5. Double-click the Square-whatever composition 6. Re-import the original footage 7. Click File/Interpret Footage/Main and be sure to check the frame rate and pixel aspect. 8. Rewind to the beginning of the shot 9. Drag the re-imported footage from the project window into the timeline as the first layer 10.Tracker nulls have a corner at the active point, instead of being centered on the active point as in SynthEyes. After Effects 2-D Procedure 1. Select one or more trackers to be exported. 2. Export using the After Effects 2-D Clipboard. You can select either the 2-D tracking data, or the 3-D position of tracker re-projected to 2-D. 3. Open the text file produced by the export 4. In the text editor, select all the text, using control-A or command-A. 5. Copy the text to the clipboard with control-C or command-C. 6. In After Effects, select a null to receive the path. 7. Paste the path into it with control-V or command-V. Bentley MicroStation You can exporter to Bentley s Microstation V8 XM Edition by following these directions. Exporting from SynthEyes MicroStation requires that animated backgrounds consist of a consecutive sequence of numbered images, such as JPEG or Targa images. If necessary, the Preview Movie capability in SynthEyes s Perspective window can be used to convert AVIs or MOVs to image sequences. Perform tracking, solving, and coordinate system alignment in SynthEyes. (Exporting coordinates from MicroStation into SynthEyes may be helpful) File/Export/Bentley MicroStation to produce a MicroStation Animation (.MSA) file. Save the file where it can be conveniently accessed from MicroStation. The export parameters are listed below. SynthEyes/MicroStation Export Parameters Target view number. The view number inside MicroStation to be animated by this MSA file (usually 2) Scaling. This is from MicroStation s Settings/DGN File Settings/Working Units, in the Advanced subsection the resolution. By default, it is listed as 10000 per distance meter, but if you have changed it for your DGN file, you must have the same value here. Relative near-clip. Controls the MicroStation near clipping-plane distance. It is a “relative” value, because it is multiplied by the SynthEyes world size setting. Objects closer than this to the camera will not be displayed in MicroStation. Relative view-size.Another option to adjust as needed if everything is disappearing from view in MicroStation. Relative far-clip. Controls the MicroStation far clipping-plane distance. It is a “relative” value, because it is multiplied by the SynthEyes world size setting. Objects farther than this from the camera will not be displayed in MicroStation. Importing into MicroStation Open your existing 3-D DGN file. Or, create a new one, typically based on seed3d.dgn Open the MicroStation Animation Producer from Utilities/Render/Animation File/Import .MSA the .msa file written by the SynthEyes exporter. Set the View Size correctly—this isrequiredto get a correct camera match. Settings/Rendering/View Size Select the correct view # (typically 2) Turn off Proportional Resize Set X and Y sizes as follows. Multiply the height(Y) of your image, in pixels, by the aspect ratio (usually 4 3 for standard video or 16 9 for HD) to get the width(X) value. For example, if your source images are 720x480 with a 4 3 aspect ratio, the width is 480*4/3 = 640, so set the image size to X=640 and Y=480, either directly on the panel or using the “Standard” drop-down menu. This process prevents horizontal (aspect-ratio) distortion in your image. Hit Apply Turn Proportional Resize back on Close the view size tool On the View Attributes panel, turn on the Background checkbox. Bring up the Animation toolbar (Tools/Visualization/Animation) and select the Animation Preview tool. You can dock it at the bottom of MicroStation if you like. If you scrub the current time on the Animation Preview, you’ll move through your shot imagery, with synchronized camera motion. Unless you have some 3-D objects in the scene, you won’t really be able to see the camera motion, however. If desired, use the Tools/3-D Main/3-D Primitives toolbar to create some test objects (as you probably did in SynthEyes). To see the camera cone of the camera imported from SynthEyes, bring up Tools/Visualization/Rendering, and select the Define Camera tool. Select the view with the SynthEyes camera track as the active view in the Define Camera tool, and turn on the Display View Cone checkbox. Transferring 3-D Coordinates If you would like to use within MicroStation the 3-D positions of the trackers, as computed by SynthEyes, you can bring them into MicroStation as follows. You have the option of exporting only a subset of points from SynthEyes to MicroStation. All trackers are exported by default; turn off the Exportable checkbox on the coordinate system panel for those you don’t wish to export. You may find it convenient to select the ones you want, then Edit/Invert Selection, then turn off the box. In SynthEyes, File/Export/Plain Trackers with Set Names=none, Scale=1, Coordinate System=Z Up. This export produces a .txt file listing all the XYZ tracker coordinates. In MicroStation, bring up the Tools/Annotation/XYZ Text toolbar. Click the Import Coordinates tool. Select the .txt file exported from SynthEyes in Step 1. Set Import=Point Element, Order=X Y Z, View=2 (or whichever you are using). Transferring Meshes SynthEyes uses two types of meshes to help align and check camera matches mesh primitives, such as spheres, cubes, etc; and tracker meshes, built from the computed 3-D tracker locations. The tracker meshes can be used to model irregular areas, such as a contoured job site into which a model will be inserted. Both types of models can be transferred as follows In SynthEyes, select the mesh to be exported, by clicking on it or selecting it from the list on the 3-D panel. Select the File/Export/STL Stereolithography export, and save the mesh to a file. In MicroStation, select File/Import STL and select the file written in step 2. You can use the default settings. Meshes will be placed in MicroStation at the same location as in SynthEyes. You can bring up its Element/Information and assign it a material. To Record the Animation Select the Record tool on the Animation toolbar (Tools/Visualization/Animation) Important Be sure the correct (square pixels) output image size is selected, the same one as the viewport size. For example, if your input is 4 3 720x480 DV footage, youMUSTselect640x480output to achieve 4 3 with square pixels (ie 640/480 = 4/3). MicroStation always outputs square pixels. You can output images with any overall aspect you wish, as long as the pixels are square (pixelaspect ratio is 1.0). Note that HD images already have square pixels. Don’t clobber your input images! Be sure to select a different location for your output footage than your input. Blender Directions Blender has a tendency to change around frequently, so the details of these directions might best be viewed more as a guide than the last word. When working with image sequences and blender, it will be a good idea to ensure that the overall frame number is the same as the number in the image file name. Although you can adjust the offset, Blender incorrectly eliminates a frame number of zero. 1. In SynthEyes, export to Blender (Python) 2. Start Blender 3. Delete the default cube and light 4. Change one of the views to the blender Text Editor 5. In the text editor, open the blender script you exported in step 1. 6. Hit ALT-P to run the script 7. Select the camera (usually Camera01) in the 3-D Viewport 8. In a 3-D view, select Camera on the View menu to look through the imported, animated, SynthEyes camera 9. Select View/Background image 10.Click Use Background Image 11.Select your image sequence or movie from the selection list. 12.Adjust the background image settings to match your image. Make sure the shot length is adequate, and that Auto Refresh is on. If the images and animation do not seem to be synced correctly, you probably have to adjust the offset. 13.Decrease the “blend” value to zero, or you can go without the background, and set up compositing within blender. 14.On the View Properties dialog, you might wish to turn off Relationship Lines to reduce clutter. 15.Use a Timeline view to scrub through the shot. Cinema 4D Procedure 1. Export from SynthEyes in Lightwave Scene format (.lws) — see below. 2. Start C4D, open the .lws file 3. From the Objects menu, add a Background 4. Create a new Texture with File/New down below. 5. At right, click on “…” next to the file name for texture. 6. Select your source file. 7. Click on the right-facing triangle button next to the file name, select Edit. 8. Select the Animation panel 9. Click the Calculate button at the bottom. 10.Drag the new texture from the texture editor onto the “Background” on the object list. Background now appears in the viewport. DotXSI Procedure 1. In SynthEyes, after completing tracking, do File/Export/dotXSI to create a .xsi file somewhere. 2. Start Softimage, or do a File/New. 3. File/Import/dotXSI... of the new .xsi file from SynthEyes. The options may vary with the XSI version, but you want to import everything. 4. Set the camera to Scene1.Camera01 (or whatever you called it in SynthEyes). 5. Open the camera properties. 6. In the camera rotoscopy section, select New from Source and then the source shot. 7. Make sure “Set Pixel Ratio to 1.0” is on. 8. Set “Use…” pixel ratio to “Camera Pixel Ratio” (should be the default) 9. In the Camera section, make sure that Field of View is set to Horizontal. 10.Make sure that the Pixel Aspect Ratio is correct. In SynthEyes, select Shot/Edit Shot to see the pixel aspect ratio. Make sure that XSI has the exact same value 0.9 isnota substitute for 0.889, so fix it! Back story XSI does not have a setting for 720x480 DV, and 720x486 D1 causes errors! 11.Close the camera properties page. 12.On the display mode control (Wireframe, etc), turn on Rotoscope. ElectricImage The ElectricImage importer relies on a somewhat higher level of user activity than normal, in the absence of a scripting language for EI. You can export either a camera or object path, and its associated trackers. 1. After you have completed tracking in SynthEyes, select the camera/object you wish to export from the Shots menu, then select File/Export/Electric Image. SynthEyes will produce two files, an .obm file containing the trajectory, and an .obj file containing geometry marking the trackers. 2. In ElectricImage, make sure you have a camera/object that matches the name used in SynthEyes. Create new cameras/objects as required. If you have Camera01 in SynthEyes, your camera should be Camera 1 in EI. The zero is removed automatically by the SynthEyes exporter. 3. Go to the Animation pull-down menu and select the Import Motion option. 4. In the open dialog box, select All Files from the Enable pop-up menu, so that the .obm file will be visible. 5. Navigate to, and select, the .obm file produced by SynthEyes. This will bring up the ElectricImage motion import dialog box which allows you to override values for position, rotation, etc. Normally, you will ignore all these options as it is simpler to parent the camera/object to an effector later. The only value you might want to change is the start time to offset when the camera move begins. Click OK and you will get a warning dialog about the frame range. This is a benign warning that sets the range of frames rendering option to match the length of the incoming camera data. Hitting cancel will abort the operation, so hit OK and the motion data will be applied to the camera. 6. Select Import Object from the Object pull-down menu. 7. Enable All Files in the pop-up menu. 8. Select the .obj file produced by SynthEyes. 9. Create a hierarchy by selecting one tracker as the parent, or bringing in all trackers as separate objects. 10.If you are exporting an object path, parent the tracker object to the object holding the path. Fusion 5 There are several Fusion-compatible exporters. The main exporter is the Fusion 5 composition export, which can be opened directly in Fusion. The Tracker 2-D Paths export can write all the exportable trackers to a text file, which can then be read in Fusion with the Import SynthEyes Trackers script and assigned to any Point-type input on a node. Select a node and start the Import script from its right-click menu. At present, it appears that you should animate the desired control before importing, then tell the script to proceed anyway when it notices that the control is already animated. There is also a generic 2-D path exporter for Fusion. Houdini Instructions 1. File/New unless you are addding to your existing scene. 2. Open the script Textport 3. Typesource c /shots/scenes/flyover.cmd or equivalent. 4. Change back from COPs to OBJs. Lightwave The Lightwave exporter produces a lightwave scene file (.lws) with several options, one of them crucial to maintaining proper synchronization. As mentioned earlier, Lightwave requires a units setting when exporting from SynthEyes. The SynthEyes numbers are unitless by changing the units setting in the lightwave exporter as you export, you can make that 24 in SynthEyes mean 24 inches, 24 feet, 24 meters, etc. This is different than in Lightwave, where changing the units from 24 inches would yield 2 feet, 0.61 meters, etc. This is the main setting that you may want to change from scene to scene. Lightwave has an obscure preferences-like setting on its Compositing panel (on the Windows menu) named “Synchronize Image to Frame.” The available options are zero or one. Selecting one shifts the imagery one frame later in time, and this is the Lightwave default. However, for SynthEyes, a setting of zero will generally be more useful (unless the SynthEyes preferenceFirst Frame is 1is turned on). The Lightwave exporter from SynthEyes allows you to select either 0 or 1. We recommend selecting zero, and adjusting Lightwave to match. You will only have to do this once, Lightwave remembers it subsequently. In all cases, you must have a matching value on the exporter UI and in Lightwave, or you will cause a subtle velocity-dependent error in your camera matches in Lightwave that will drive you nuts until you fix the setting. The exporter also has a checkbox for using DirectShow. This checkbox applies only for AVIs, and should be on for most AVIs that contain advanced codecs such as DV or HD. If an AVI uses an older codec and is not opened automatically within Lightwave, export again with this checkbox turned off. Nuke The nuke exporter produces a nuke file you can open directly. The pop-up parameter panel lets you indicate if you have a slate frame at the start of the shot, or select renderable or non-rendering tracker marks. The renderable marks are better for tracking, the non-rendering marks better for adding objects within Nuke s 3-D view. Poser Poser struggles a little to be able to handle a match-moved camera, so the process is a bit involved. Hopefully Curious Labs will improve the situation in further releases. The shot must have square pixels to be used properly by Poser; it doesn t understand pixel aspect ratios. So if you have a 720x480 DV source, say, you need to resample it in SynthEyes, AfterEffects or something to 640x480. Also, the shot has to have a frame rate of exactly 30 fps. This is a drag since normal video is 29.97 fps, and Poser thinks it is 29.00 fps, and trouble ensues. One way to get the frame rate conversion without actually mucking up any of the frames is to store the shot out as a frame sequence, then read it back in to your favorite tool as a 30 fps sequence. Then you can save the 640x480 or other square-pixel size. Note that you can start with a nice 720x480 29.97 DV shot, track it in SynthEyes, convert it as above for Poser, do your poser animation, render a sequence out of Poser, then composite it back into the original 720x480. One other thing you need to establish at this time---exactly how many frames there are in your shot. If the shot ranges are 0 to 100, there are 101; from 10 to 223, there are 214. 1. After completing tracking in SynthEyes, export using the Poser Python exporter. 2. Start Poser. 3. Set the number of frames of animation, at bottom center of the Poser interface, to the correct number of frames. It is essential that you do this now, before reading the python script 4. File/Run Python Script on the python script output from SynthEyes. 5. The Poser Dolly camera will be selected and have the SynthEyes camera animation on it. There are little objects for each tracker, and also SynthEyes boxes, cones, etc are brought over into Poser. Open Question How to render out of Poser with the animated movie background. The best approach appears to be to render against black with an alpha channel, then composite over the original shot externally. Shake SynthEyes offers three specific exporters for Shake, plus one generic one 1. MatchMove Node. 2. Tracker Node 3. Tracking File format 4. 3-D Export via the “AfterFX via .ma” or Maya ASCII exports. The first two formats (Sizzle export scripts) produce shake scripts (.shk files); the third format is a text file. The fourth option produces Maya scene files that Shake reads and builds into a scene using its 3-D camera. We’ll start with the simplest, the tracking file format. Select one tracker and export with the Shake Tracking File Format, and you will have a track that can be loaded into a Shake tracker using the load option. You can use this to bring a track from SynthEyes into existing Shake tracking setups. Building on this basis, #2, Tracker Node, exports one or more selected trackers from SynthEyes to create a single Tracker Node within Shake. There are some fine points to this. First, you will be asked whether you want to export the solved 3-D positions, or the tracked 2-D positions. These values are similar, but not the same. If you have a 3-D solution in SynthEyes, you can select the solved 3-D positions, and the export will be the “ideal” tracked (predicted) coordinates, with less jitter than the plain 2-D coordinates. Also, since you might be exporting from a PC to a Mac or Linux machine, the image source file(s) may be named differently perhaps X \shots1\shot1_#.tga on the PC, and //macmachine/Users/tom/shots/shot1_#.tga on the PC. The Shake export script s dialog box has two fields, PC Drive and Mac Drive, that you can set to automatically translate the PC file name into the Mac file name, so that the Shake script will work immediately. In this example, you would set PC Drive to “X \\” and Mac Drive to “//macmachine/Users/tom/”. Finally, the MatchMove node exporter looks not for trackers to export, but for SynthEyes planes! Each plane (created from the 3-D panel) is exported to Shake by creating four artificial trackers (in Shake) at the corners of the plane. The matchmove export lets you insert a layer at any arbitrary position within the 3-D environment calculated by SynthEyes. For example, you can insert a matte painting into a scene at a location where there is nothing to track. You can use a collection of planes, positioned in SynthEyes, to obtain much of the effect of a 3-D camera. The matchmove node export also provides PC to Mac/Linux file name translation. trueSpace Directions Warning trueSpace has sometimes had problems executing the exported script correctly. Hopefully Caligari will fix this soon. 1. In SynthEyes, export to trueSpace Python. 2. Open trueSpace. 3. Right-click the Play button in the trueSpace animation controls. 4. Set the correct BaseRate/PlayRate in the animation parameters to match your source shot. 5. Open the Script Editor. 6. From inside the Script Editor, Open/Assign the python script you created within SynthEyes. 7. Click Play (Time On) in the Script Manager. 8. When the Play button turns off, close the ScriptManager. 9. Open the Object Info panel. 10.Verify that the SynthEyes camera is selected (usually Camera01). 11.Change the Perspective view to be View from Object. 12.Select the Camera01Screen. 13.Open the Material Editor (paint pallete). 14.Right click on Color shaders button. 15.Click on (Caligari) texture map, sending it to the Material Editor color shader. 16.Open the subchannels of the Material Editor (Color, Bump, Reflectance). 17.On the Color channel of the Material Editor, right click on the Get Texture Map button and select your source shot. 18.Check the Anim box. 19.Click the Paint Object button on the Material Editor. 20.Click on File/Display Options and change the texture resolution to 512x512. 21.You may want to set up a render background to overlay animated objects on the background, or you can use an external compositing program. Make the Camera01Screen object invisible before rendering. 22.In trueSpace, you need to pay special attention to get the video playback synchronized with rest of the animation, and to get the render aspect ratio to match the original. For example, you must add the texture map while you are at frame zero, and you should set the pixel aspect ratio to match the original (SynthEyes s shot panel will tell you what it is). Vue 5 Infinite The export to Vue Infinite requires a fair number of manual steps pending further Vue enhancements. But with a little practice, they should only take a minute or two. 1. Export from SynthEyes using the Vue 5 Infinite setting. The options can be left at their default settings unless desired. You can save the python script produced into any convenient location. 2. Start Vue Infinite or do a File/New in it. 3. Select the Main Camera 4. On its properties, turn OFF Always keep level 5. Go to the animation menu, turn ON the auto-keyframe option. 6. Select the Python/Run python script menu item, select the script exported from SynthEyes, and run it. 7. In the main camera view, select the Camera01 Screen object (or the equivalent if the SynthEyes camera was renamed) 8. In the material preview, right-click, select Edit Material. 9. The material editor appears, select Advanced Material Editor if not already. 10.Change the material name to flyover or whatever the image shot name is. 11.Select the Colors tab. 12.Select Mapped picture 13.Click the left-arrow Load icon under the black bitmap preview area 14.In the Please select a picture to load dialog, click the Browse File icon at the bottom --- a left arrow superimposed on a folder 15.Select your image file in the Open Files dialog. If it is an image sequence, select the first image, then shift-select the last. 16.On the material editor, under the bitmap preview area, click the clap-board animation icon to bring up the Animated Texture Options dialog 17.Set the frame rate to the correct value. 18.Turn on Mirror Y 19.Hit OK on the Animated Texture dialog 20.On the drop-down at top right of the Advanced Material Editor, select a Mapping of Object- Parametric 21.Turn off Cast shadows and Receive shadows 22.Back down below, click the Highlights tab 23.Turn Highlight global intensity down to zero. 24.Click on the Effects tab 25.Turn Diffuse down to zero 26.Click the Ambient data-entry field and enter 400 27.Hit OK to close the Advanced Material Editor 28.Select the Animation/Display Timeline menu item (or hit F11) 29.If this is the first time you have imported from SynthEyes to Vue Infinite, you must perform the following steps a. Select File/Options menu item. b. Click the Display Options tab c. Turn off Clip objects under first horizontal plane in main view only , otherwise you will not be able to see the background image. d. Turn off Clip objects under first horizontal plane (ground / water) e. Turn off Stop camera going below clipping plane (ground / water) if needed by your camera motion. f. Hit OK 30.Delete the Ground object 31.If you are importing lights from SynthEyes, you can delete the Sun Light as well, otherwise, spin the Sun Light around to point at the camera screen, so that the image can be seen in the preview window. 32.You may have to move the time bar before the image appears. Vue Infinite only shows the first image of the sequence, so you can verify alignment at frame zero. 33.You will later want to disable the rendering of the trackers, or delete them outright. 34.Depending on what you are doing, you may ultimately wish to delete or disable the camera screen as well, for example, if you will composite an actor in front of your Vue Infinite landscape. 35.The import is complete; you can start working in Vue Infinite. You should make probably save a copy of the main camera settings so that you can have a scratch camera available as you prepare the scene in Vue Infinite. Vue 6 Infinite Export from SynthEyes using the Vue 6 Infinite option, producing a maxscript file. Import the maxscript file in Vue 6 Infinite Adjust the aspect ratio of the backdrop to the correct overall aspect ratio for your shot. This is important since Vue assumes square pixels, and if they aren’t (for all DV, say), the camera match will be off badly
https://w.atwiki.jp/pathofexile12/pages/920.html
No TracesはDivination Cardの一種 交換可能アイテム 入手方法 関連リンク No Traces 必要枚数 9枚 30xOrb of Scouring There is no mistake so great that it cannot be undone. 交換可能アイテム 変換先 Orb of Scouring 入手方法 このカードがドロップするエリア The Ossuary (Act 5) • The Reliquary (Act 10) • The Ossuary (Act 10) • Mausoleum Map • Relic Chambers Map • Sepulchre Map カード等のドロップ以外の入手方法 アイテム 必要数 備考 The Gambler 5 Stacked Deck 1 関連リンク 英wiki https //pathofexile.gamepedia.com/No_Traces Divination Card